Okay, that worked. I guess Buildkite doesn't want to run on #50394 because #50394 was created before the julia-release-1.10 pipeline was created.

Just so you're aware, there's some discussion in #49805 about a potential issue with a previous PR feature-wise, that would be resolved with that PR (that just didn't seem to get merged before the feature freeze..)

@nanosoldier runtests(ALL, vs = ":release-1.9", configuration = (buildflags=["LLVM_ASSERTIONS=1", "FORCE_ASSERTIONS=1"],), vs_configuration=(buildflags=["LLVM_ASSERTIONS=1", "FORCE_ASSERTIONS=1"],))

@nanosoldier runbenchmarks(ALL, vs = ":release-1.9")

This is just an alpha so it basically provides no guarantees.

Your benchmark job has completed - possible performance regressions were detected. A full report can be found here.

@DilumAluthge, what was the reason for rerunning nanosoldier? It's already running on the previous PR.

Your package evaluation job has completed - possible new issues were detected.
A full report can be found here.

Ah, I just assumed that when the old PR was closed, it would auto-cancel the Nanosoldier job. (Similar to how when you delete a branch, Buildkite auto-cancels the CI run on that branch.)